refactor(ledger): rename goldseal@v1 certificate → korgcert@v1#18
Merged
Conversation
Kills the goldseel (policy model) vs goldseal (certificate format) near-homograph by renaming the certificate. The model is untouched. Schema string, verifier, spec, docs, fixtures (re-minted + re-signed), CI, and python/js adapters all move together so signatures still verify (Rust + JS + Python conformance green). Display 'Gold Seal' -> 'Certificate'.
New1Direction
force-pushed
the
rename/goldseal-to-korgcert
branch
from
738eee1 to
522a565
Compare
🛡️ ✅ Certificate verifiedIndependently verified — zero trust in the tool that produced it. ✅
|
| claim | CI demo: agent added a /healthz endpoint with a passing test |
| who (issuer) | a9a4d67bd8e504c9… |
| what | 5 events · Bash×1 Edit×1 Read×1 Write×1 user_prompt×1 |
| files | src/app.py, tests/test_health.py |
| integrity | chain ✓ · summary re-derived ✓ · seal ✓ |
Verified by the independent korg verifier. Re-check in a browser: seal.html.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Rename the ledger certificate format
goldseal@v1→korgcert@v1("Certificate").Why
goldseel(the policy model) andgoldseal(this certificate format) were oneletter apart and meant completely different things — a real footgun. Renaming the
format kills the collision; the model keeps its name and stands alone.
What changed (39 files)
KORGCERT.md) + docs + CI + fixtures + Python/JS adapters — all moved together.schemalives inside the signedseal_header, so fixtures were re-minted + re-signed (deterministic, seed[42]*32).Verified
korg-verify: 9/9 + thekorgcertsuite 7/7 (the 3 that broke are green).verify.mjs:korgcert VALID. Python-minted → Rust-verified passes.cargo build --workspace: clean.0goldseal-format refs remain.Untouched (on purpose)
The
goldseelmodel + its live endpoint, the@quaestor/*npm, and thegoldseal.glbbrand visual.